✅ Deploy Preview for incomparable-parfait-2417f8 ready!

Name	Link
🔨 Latest commit	3c3259e
🔍 Latest deploy log	https://app.netlify.com/projects/incomparable-parfait-2417f8/deploys/6936c5f1d194cf00080acbd7
😎 Deploy Preview	https://deploy-preview-271--incomparable-parfait-2417f8.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

🚀 Deployed on https://6a554c107f478f75d3471d68--incomparable-parfait-2417f8.netlify.app

✅ Deploy Preview for incomparable-parfait-2417f8 ready!

Name	Link
🔨 Latest commit	cae4b89
🔍 Latest deploy log	https://app.netlify.com/projects/incomparable-parfait-2417f8/deploys/6a55497059433700086d0251
😎 Deploy Preview	https://deploy-preview-271--incomparable-parfait-2417f8.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

CC @mmcky — flagging a preview-deploy issue on this PR that looks like a build-system problem rather than anything in the content.

Symptom: the "Deploy Preview" link that the Netlify GitHub app advertises 404s:

• https://deploy-preview-271--incomparable-parfait-2417f8.netlify.app → 404 (both / and /arellano.html)

But the build actually succeeded and is live — just under the permalink, not the alias:

• https://6a554c107f478f75d3471d68--incomparable-parfait-2417f8.netlify.app → 200 (/arellano.html and /intro.html both serve fine)

The latest CI run for arellano_update (commit cae4b89) completed successfully, and GitHub's deployment API maps that run's deploy to the permalink above (ref cae4b891…, state success, 2026-07-13).

Likely cause: this repo runs two Netlify integrations in parallel:

1. The official Netlify GitHub app, which owns the deploy-preview-271--… alias and posts the "✅ Deploy Preview ready" comment.
2. The nwtgck/actions-netlify step in .github/workflows/ci.yml, which publishes from _build/html/ and posts the 🚀 Deployed on <permalink> comment.

The actions-netlify step is publishing a working build (hence the live permalink), but the deploy-preview-271 alias the Netlify app comment points at is detached from that build — so the link everyone clicks 404s while the content is actually up. Having both integrations deploy to the same site is probably the root of the collision.

Could you take a look at the build system when you get a chance? The fix is likely either dropping one of the two integrations or making sure the alias is bound to the actions-netlify deploy. Happy to help test.

@kp992 Many thanks! All looks good. I'll merge now.

@mmcky A comment above from Claude about issues with finding the live deployment. I'm not sure if it's worth fixing before the switch one the monorepo. I guess it depends how we're going to handle existing PRs.

Thanks for merging this @jstac

@jstac spot-on diagnosis, thanks for tracking that down. It was exactly the two-integration collision you described — the official Netlify GitHub app owned the deploy-preview-271 alias and its comment, while the nwtgck/actions-netlify step published the actual working build under a detached permalink.

Fixed in #336 (merged):

• Migrated the preview step to the org-standard quantecon/actions/preview-netlify@v0.8.0 (same as lecture-python.myst). It deploys via the Netlify CLI to a deterministic pr-<N> alias and posts a single self-updating comment with direct links to the changed lecture pages, so the link in the comment is always the one bound to the build.
• Removed the redundant Netlify deploy from collab.yml — a second actions-netlify step that was racing the same site/alias and publishing a lesser build (no notebook/PDF assets).